Hello!


FILE LIST
=========

The avtavr.zip contains the following files:

MAIN DRIVER FILE:
avtavr.llb  - the Labview VI library, with the driver VIs.
avtavru.llb - the Labview VI utility library, with low level utility VIs 
               which are not intended to be called or modified by the user

MENU PALETTE FILES:
applic.mnu
config.mnu
data.mnu
dir.mnu
util.mnu

OTHER FILES:
avtavr.txt - this file


HOW TO INSTALL THE DRIVER
=========================

Locate the "National Instruments\LabVIEW\INSTR.LIB" directory. 
Create a new directory in it, called "avtavr".
Copy all of the files listed above into the "avtavr" directory.
Start, or restart, LabView.

Once Labview has restarted, go to a block diagram and bring up the
Functions palette. Look in the Instrument Drivers subpalette. You
should see an icon for the avtavr driver.


HOW TO MODIFY THIS DRIVER
=========================

This driver is intended for standard AVR-type Avtech models.
However, since all Avtech instruments with the "-B" or "-OP1B"
suffixes share the same basic command set (which in turn is based
on the SCPI standard), you can modify this driver to control
another model.

Here are some things to keep in mind when modifying this driver:

1) If your instrument is a current pulser rather than a voltage
pulser, you will need to modify the 
"AVTAVR Set Value of Voltage Amplitude.vi" block diagram. Change
the "volt%d %e" string to "curr%d %e".

2) The configuration VIs are written to accomodate multi-channel
instruments. If you have a multi-channel instrument, you will have
to add channel controls to "AVTAVR Application Example.vi",
and connect them to the configuration VIs' existing channel inputs,
where appropriate (i.e., only for functions that have multi-channel
capability.)

3) You may need to enable/disable choices on the PW mode and amplitude
mode controls in "AVTAVR Application Example.vi", to reflect the
functionality of your instrument. Do not delete unused entries - just
disable them. (If you delete a choice, the integer number associated
with each entry may become incorrect.)

4) The default pulse width values in the Application Example and 
Getting Started VIs may need to increased for some slower models.
(This is basically just a cosmetic change.)


FEEDBACK
========

Does this driver meet your needs? Does it have obvious flaws?
Either way, we'd like to hear about it. Please send comments to:

Dr. Michael J. Chudobiak
VP, New Product Development
mjc@avtechpulse.com

General inquiries should be directed to info@avtechpulse.com,
for fastest service.

Visit us at www.avtechpulse.com!
